home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.20041116-20060924 / 000337_edgage@gmail.com_Sat May 6 15:11:11 2006.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB
  1. Path: newsmaster.cc.columbia.edu!newsfeed.nyu.edu!news.maxwell.syr.edu!postnews.google.com!i40g2000cwc.googlegroups.com!not-for-mail
  2. From: "Ed Gage" <edgage@gmail.com>
  3. Newsgroups: comp.protocols.kermit.misc
  4. Subject: Another Secure FTP thread -- Protection Levels
  5. Date: 5 May 2006 13:32:01 -0700
  6. Organization: http://groups.google.com
  7. Lines: 34
  8. Message-ID: <1146861121.842424.256350@i40g2000cwc.googlegroups.com>
  9. NNTP-Posting-Host: 65.175.9.114
  10. Mime-Version: 1.0
  11. Content-Type: text/plain; charset="iso-8859-1"
  12. X-Trace: posting.google.com 1146861130 8602 127.0.0.1 (5 May 2006 20:32:10 GMT)
  13. X-Complaints-To: groups-abuse@google.com
  14. NNTP-Posting-Date: Fri, 5 May 2006 20:32:10 +0000 (UTC)
  15. User-Agent: G2/0.2
  16. X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
  17. Complaints-To: groups-abuse@google.com
  18. Injection-Info: i40g2000cwc.googlegroups.com; posting-host=65.175.9.114;
  19.    posting-account=n2RQvg0AAACdyE7hdyUFKqejJdt16fuE
  20. Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15594
  21.  
  22. Read through the other FTP thread -- very helpful.
  23.  
  24. The obstacle I'm dealing with is connecting to a secure FTP server
  25. through our router.  I'm behind a Linksys router which for some reason
  26. doesn't like to read encrypted packets.
  27.  
  28. Here's what I tried with a newly-compiled CKERMIT 8.12:
  29.  
  30. set ftp autoencryption off
  31. set ftp authtype ssl
  32. set ftp command-protection-level clear
  33. ftp ###.###.###.### /user:##### /password:#####
  34.  
  35. It responds with:
  36. Connected to ###.###.###.###
  37. SSL accepted as authentication type
  38.  
  39. ...then the self-signed certificate issue discussed in the other
  40. thread, but not a crisis at this time.
  41.  
  42. The issue is a SHOW FTP returning:
  43.  
  44. Available security methods:
  45.  
  46.  ftp authtype:                  SSL
  47.  ftp auto-encryption:           off
  48.  ftp credential-forwarding:     off
  49.  ftp command-protection-level:  safe
  50.  ftp data-protection-level:     private
  51.  ftp secure proxy:              (not set)
  52.  
  53. How come when I set the command-protection-level to clear, it connects
  54. as safe?  Is this dictated by the server?
  55.